home *** CD-ROM | disk | FTP | other *** search
- Path: doc.ic.ac.uk!not-for-mail
- From: mdf@doc.ic.ac.uk (Martin Frost)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: Problems With LoadSeg()
- Date: 8 Feb 1996 15:25:15 -0000
- Organization: Dept. of Computing, Imperial College, University of London, UK.
- Distribution: Earth
- Message-ID: <4fd4kr$cu7@oak68.doc.ic.ac.uk>
- References: <DMF0vK.LI0@gpu.utcc.utoronto.ca>
- Reply-To: mdf@doc.ic.ac.uk (Martin Frost)
- NNTP-Posting-Host: oak68.doc.ic.ac.uk
- X-Newsreader: mxrn 6.18-23
-
-
- In article <DMF0vK.LI0@gpu.utcc.utoronto.ca>, normb@gpu.utcc.utoronto.ca (Norman Baccari) writes:
- >If I LoadSeg()
- >a library and look at the resident structures rt_IdString,
- >on certain libraries the first 4 bytes of the IdString
- >contain \0\4\251\128.
-
- I guess this is intended as an empty string (I don't think RomTags are
- required to have a name), and it's just coincidence that the name follows
- afterward.
-
- > ResLib=(struct Resident *)((LONG *)BADDR(LibSeg)+2);
-
- Don't you actually need
-
- for(ResLib=(struct Resident *)BADDR(LibSeg);
- ResLib->rt_MatchWord==0x4AFC && ResLib->rt_MatchPtr==ResLib;
- (UWORD *)ResLib++);
-
- since I don't think the RomTag is guaranteed to start at any particular place.
-
- btw, I'm not sure of the exact name for rt_MatchPtr, you'll need to check
- the includes.
-
- Martin
-